Network port connector ejection system

ABSTRACT

A network port connector ejection system includes a computing device connector that is connected to a network port connector. A retention device in the network port connector ejection system is configured to engage the network port connector to secure the network port connector to the computing device connector. A retention device release subsystem in the network port connector ejection system is coupled to the retention device and is configured to be actuated to release the retention device from engagement with the network port connector. A network port connector ejection subsystem in the network port connector ejection system is configured to engage the network port connector, while the retention device release subsystem is actuated to release the retention device from engagement with the network port connector, to disconnect the network port connector from the computing device connector.

BACKGROUND

The present disclosure relates generally to information handlingsystems, and more particularly to ejecting network port connectors frominformation handling systems.

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option available to users is information handling systems. Aninformation handling system generally processes, compiles, stores,and/or communicates information or data for business, personal, or otherpurposes thereby allowing users to take advantage of the value of theinformation. Because technology and information handling needs andrequirements vary between different users or applications, informationhandling systems may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in informationhandling systems allow for information handling systems to be general orconfigured for a specific user or specific use such as financialtransaction processing, airline reservations, enterprise data storage,or global communications. In addition, information handling systems mayinclude a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more computer systems, data storage systems, andnetworking systems.

Information handling systems such as, for example, server devices and/orother computing devices known in the art, may include server/computingdevice ports that are configured to connect to a network via networkport connectors that are coupled to network cables. For example, SmallForm-factor Pluggable (SFP) transceiver devices are often connected toserver device ports on server devices, with network cables that arecoupled to a network also connected to the SFP transceiver devices inorder to provide network connectivity for the server devices. However,such network connectivity can raise some issues such as, for example,when server devices are compromised by viruses or hacking attempts, whenunauthorized server devices are connected to a datacenter network,and/or in other situations that would be apparent to one of skill in theart. In such situations, it may be desirable to disconnect a compromisedor unauthorized server device from the network, but many server devicesare located in remote datacenters. As such, the physical disconnectionof the server device from the network via the physical disconnection ofan SFP transceiver device from the server device port on the serverdevice may not be an immediate option, and may require a networkadministrator or other user to be physically present at the serverdevice in order to disconnect the SFP transceiver device. One solutionto such issues is to remotely power off compromised or unauthorizedserver devices, but the powering off of a server device is associatedwith risks such as, for example, the inability of the powered-off serverdevice to subsequently boot or initialize correctly, and operates toprevent a network administrator or other user from subsequentlytroubleshooting the server device remotely.

Accordingly, it would be desirable to provide a network port connectorsystem that addresses the issues discussed above.

SUMMARY

According to one embodiment, an Information Handling System (IHS)includes a processing system; and a memory system that is coupled to theprocessing system and that includes instructions that, when executed bythe processing system, cause the processing system to provide a networkport connector ejection engine that is configured to: receive aninstruction to eject a network port connector that is connected to acomputing device connector; actuate, in response to receiving theinstruction to eject the network port connector, a retention devicerelease subsystem that is coupled to a retention device to release theretention device from engagement with the network port connector; andactuate, in response to receiving the instruction to eject the networkport connector, a network port connector ejection subsystem to engagethe network port connection ejection subsystem with the network portconnector, while the retention device release subsystem is actuated torelease the retention device from engagement with the network portconnector, to disconnect the network port connector from the computingdevice connector.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view illustrating an embodiment of an InformationHandling System (IHS).

FIG. 2A is a perspective view illustrating an embodiment of a networkport connector device.

FIG. 2B is a schematic view illustrating an embodiment of the networkport connector device of FIG. 2A.

FIG. 3 is a schematic view illustrating an embodiment of a network portconnector system.

FIG. 4 is a schematic view illustrating a computing device that may becoupled to the network port connector device of FIGS. 2A and 2B.

FIG. 5 is a schematic view illustrating a computing device that may becoupled to the network port connector system of FIG. 3.

FIG. 6 is a flow chart illustrating an embodiment of a method forejecting a network port connector.

FIG. 7A is a perspective view illustrating an embodiment of the networkport connector device of FIGS. 2A and 2B being connected to thecomputing device of FIG. 4 during the method of FIG. 6.

FIG. 7B is a schematic view illustrating an embodiment of the networkport connector device of FIGS. 2A and 2B being connected to thecomputing device of FIG. 4 during the method of FIG. 6.

FIG. 7C is a schematic view illustrating an embodiment of the networkport connector device of FIGS. 2A and 2B connected to the computingdevice of FIG. 4 during the method of FIG. 6.

FIG. 7D is a schematic view illustrating an embodiment of the computingdevice of FIG. 4 operating during the method of FIG. 6 to eject thenetwork port connector device of FIGS. 2A and 2B.

FIG. 7E is a schematic view illustrating an embodiment of the computingdevice of FIG. 4 operating during the method of FIG. 6 to eject thenetwork port connector device of FIGS. 2A and 2B.

FIG. 7F is a schematic view illustrating an embodiment of the computingdevice of FIG. 4 operating during the method of FIG. 6 to eject thenetwork port connector device of FIGS. 2A and 2B.

FIG. 7G is a schematic view illustrating an embodiment of the computingdevice of FIG. 4 having ejected the network port connector device ofFIGS. 2A and 2B during the method of FIG. 6.

FIG. 8A is a schematic view illustrating an embodiment of the networkport connector device of FIG. 3 connected to the computing device ofFIG. 5 during the method of FIG. 6.

FIG. 8B is a schematic view illustrating an embodiment of the computingdevice of FIG. 5 operating during the method of FIG. 6 to eject thenetwork port connector device of FIG. 3.

FIG. 8C is a schematic view illustrating an embodiment of the computingdevice of FIG. 5 operating during the method of FIG. 6 to eject thenetwork port connector device of FIG. 3.

FIG. 8D is a schematic view illustrating an embodiment of the computingdevice of FIG. 5 having ejected the network port connector device ofFIG. 3 during the method of FIG. 3.

DETAILED DESCRIPTION

For purposes of this disclosure, an information handling system mayinclude any instrumentality or aggregate of instrumentalities operableto compute, calculate, determine, classify, process, transmit, receive,retrieve, originate, switch, store, display, communicate, manifest,detect, record, reproduce, handle, or utilize any form of information,intelligence, or data for business, scientific, control, or otherpurposes. For example, an information handling system may be a personalcomputer (e.g., desktop or laptop), tablet computer, mobile device(e.g., personal digital assistant (PDA) or smart phone), server (e.g.,blade server or rack server), a network storage device, or any othersuitable device and may vary in size, shape, performance, functionality,and price. The information handling system may include random accessmemory (RAM), one or more processing resources such as a centralprocessing unit (CPU) or hardware or software control logic, ROM, and/orother types of nonvolatile memory. Additional components of theinformation handling system may include one or more disk drives, one ormore network ports for communicating with external devices as well asvarious input and output (I/O) devices, such as a keyboard, a mouse,touchscreen and/or a video display. The information handling system mayalso include one or more buses operable to transmit communicationsbetween the various hardware components.

In one embodiment, IHS 100, FIG. 1, includes a processor 102, which isconnected to a bus 104. Bus 104 serves as a connection between processor102 and other components of IHS 100. An input device 106 is coupled toprocessor 102 to provide input to processor 102. Examples of inputdevices may include keyboards, touchscreens, pointing devices such asmouses, trackballs, and trackpads, and/or a variety of other inputdevices known in the art. Programs and data are stored on a mass storagedevice 108, which is coupled to processor 102. Examples of mass storagedevices may include hard discs, optical disks, magneto-optical discs,solid-state storage devices, and/or a variety other mass storage devicesknown in the art. IHS 100 further includes a display 110, which iscoupled to processor 102 by a video controller 112. A system memory 114is coupled to processor 102 to provide the processor with fast storageto facilitate execution of computer programs by processor 102. Examplesof system memory may include random access memory (RAM) devices such asdynamic RAM (DRAM), synchronous DRAM (SDRAM), solid state memorydevices, and/or a variety of other memory devices known in the art. Inan embodiment, a chassis 116 houses some or all of the components of IHS100. It should be understood that other buses and intermediate circuitscan be deployed between the components described above and processor 102to facilitate interconnection between the components and the processor102.

Referring now to FIGS. 2A and 2B, an embodiment of a network portconnector device 200 is illustrated. One of skill in the art inpossession of the present disclosure will recognize that, in theillustrated embodiment, the network port connector device 200 isprovided by a Small Form-factor Pluggable (SFP) transceiver device.However, while illustrated and discussed as being provided by an SFPtransceiver device, one of skill in the art in possession of the presentdisclosure will recognize that network port connector devices providedin the network port connector ejection system of the present disclosuremay include any network port connector devices that may be configured tooperate similarly as the network port connector device 200/SFPtransceiver device discussed below.

In the embodiment illustrated in FIGS. 2A and 2B, the network portconnector device 200 includes a base 202 that may house the componentsof the network port connector device 200, which one of skill in the artin possession of the present disclosure will appreciate may includeprocessing systems, memory systems, storage systems, communicationsystems, and/or any network port connector device/SFP transceiver devicecomponents known in the art. A cable connector end 204 on the networkport connector device 200 defines cable connector slots 204 a and 204 b,each of which is configured to receive a cable connector and allow thatcable connector to engage a device connector included in the base 202(e.g., as part of the communication system discussed above.) A releaseelement 206 is included on the cable connector end and, in theillustrated embodiment, is coupled to a release subsystem 208 that islocated in a channel 210 defined by the cable connector end 206, asillustrated in FIG. 2B. FIG. 2B also illustrates how the base 202 mayhouse a network port connector 212 that one of skill in the art inpossession of the present disclosure will recognize may be included aspart of the communication system discussed above, and may be coupled toany or all of the components (e.g., the processing system discussedabove) housed in the base 202. However, while a specific network portconnector on a network port connector device 200 has been illustratedand described in FIGS. 2A and 2B, one of skill in the art in possessionof the present disclosure will recognize that network port connectorsutilized in the present disclosure may include a variety of network portconnectors while remaining within the scope of the present disclosure aswell.

For example, FIG. 3 illustrates an embodiment of a network portconnector system 300 that one of skill in the art in possession of thepresent disclosure will recognize is provided by an Ethernet cablingsystem. However, while illustrated and discussed as being provided by anEthernet cabling system, one of skill in the art in possession of thepresent disclosure will recognize that network port connector systemsprovided in the network port connector ejection system may include anynetwork port connector system that may be configured to operatesimilarly as the network port connector system 300/Ethernet cablingsystem discussed below. In the embodiment illustrated in FIG. 3, thenetwork port connector system 300 includes a base 302 that may housesome of the components of the network port connector system 300, whichone of skill in the art in possession of the present disclosure willappreciate may include a variety of communication system componentsand/or any network port connector system/Ethernet cabling systemcomponents known in the art. A cable 304 extends from the base 302 ofthe network port connector system 300, and may be provided by a varietyof Ethernet cabling (e.g., CAT5 cabling and/or other cabling known inthe art.) A network port connector 306 is included on the base 302opposite the base 302 from the cable 304, and a retention member 308extends from the base 302 opposite the base 302 from the cable 304 aswell.

Furthermore, while two specific examples of devices and systems aredescribed herein that provide network port connectors that may beutilized with the network port connector ejection system of the presentdisclosure, one of skill in the art in possession of the presentdisclosure will appreciate that other devices and systems such asnetwork cards, network daughter cards, and/or other networking systemswill benefit from the teachings of the present disclosure as well.Furthermore, while the discussion herein is focused on networkingfunctionality provided via network port connections, one of skill in theart will appreciate that the teachings of the present disclosure may beapplied to connectors that provide a connection to systems other than anetwork while remaining within the scope of the present disclosure aswell.

Referring now to FIG. 4, an embodiment of a computing device 400 isillustrated that may provide the network port connector ejection systemof the present disclosure. In an embodiment, the computing device 400may be provided by the IHS 100 discussed above with reference to FIG. 1and/or may include some or all of the components of the IHS 100, and inspecific examples may be provided by a server device. However, whileillustrated and discussed as being provided by a server device, one ofskill in the art in possession of the present disclosure will recognizethat the functionality of the computing device 400 discussed below maybe provided by other devices that are configured to operate similarly asthe computing device 400 discussed below (e.g., storage systems, switchdevices and/or other networking devices, and/or any other devicesincluding network ports.) In the illustrated embodiment, the computingdevice 400 includes a chassis 401 that houses the components of thecomputing device 400, only some of which are illustrated below. Forexample, the chassis 401 may house a processing system (not illustrated,but which may include the processor 102 discussed above with referenceto FIG. 1) and a memory system (not illustrated, but which may includethe memory 114 discussed above with reference to FIG. 1) that is coupledto the processing system and that includes instructions that, whenexecuted by the processing system, cause the processing system toprovide a network port connection ejection engine 402 that is configuredto perform the functionality of the network port connection ejectionengines and/or computing devices discussed below. In some examples, thenetwork port ejection engine 402 may be provided by a dedicated softwareprogram (e.g., that may be remotely operated), a management utilityprogram, via a remote access controller interface (as discussed below),and/or in a variety of other manners that would be apparent to one ofskill in the art in possession of the present disclosure. Furthermore,one of skill in the art in possession of the present disclosure willappreciate that the network port ejection engine 402 may includefirmware and, in some cases, electronics that are configured to operateand monitor the state of the network port connector ejection system.

As illustrated, the chassis 400 may also house a communication system404 that is coupled to the network port connection ejection engine 402(e.g., via a coupling between the communication system 404 and theprocessing system) and that may be provided by a Network InterfaceController (NIC), wireless communication systems (e.g., BLUETOOTH®, NearField Communication (NFC) components, WiFi components, etc.), and/or anyother communication components that would be apparent to one of skill inthe art in possession of the present disclosure. In a specific example,the computing device 400 may include a remote access controller such asa Baseboard Management Controller (BMC) like the integrated DELL® RemoteAccess Controller (iDRAC) available from DELL® Inc. of Round Rock, Tex.,United States, and the remote access controller may include the networkport connection ejection engine 402, along with the communication system404 illustrated in FIG. 4 that may be coupled to a secure managementnetwork that allows for secure management of the computing device 400.However, one of skill in the art in possession of the present disclosurewill appreciate that remote access controllers may be provided outsideof a chassis of a computing device, and thus the network port connectionejection engine 402 and communication system 404 may be located outsideof the chassis 401 while remaining within the scope of the presentdisclosure as well.

In the embodiment illustrated in FIG. 4, the computing device 400includes a wall 406 defining a network port connector device slot 408,and a board 410 (e.g., a circuit board or motherboard) is located in thechassis 401 adjacent the network port connector device slot 408. Acomputing device connector 412 in mounted to the board 410, and one ofskill in the art in possession of the present disclosure will recognizethat the computing device connector 412 may be coupled to components ofthe computing device 400 (e.g., the processing system, memory system,and/or other components discussed above) via traces that extend throughthe board, via cabling, and/or via other coupling subsystems known inthe art. A retention device 414 is included on or coupled to the board410, and in some of the embodiments discussed below the retention devicemay include and/or be fabricated from a metal material. For example, theretention device 414 may be provided by a spring-biased metal latch thatis configured to secure the network port connector device 200 in thenetwork port connector device slot 408, although one of skill in the artin possession of the present disclosure will appreciate that a varietyof different types of retention devices will fall within the scope ofthe present disclosure as well. In the illustrated embodiment, aretention device release subsystem 416 is located adjacent the retentiondevice 414 and coupled to the network port connector ejection engine 402(e.g., via a coupling between the retention device release subsystem 416and the processing system in the remote access controller discussedabove). In a specific example, the retention device release subsystem416 may be provided by an electromagnet subsystem that is mounted to theboard 410 opposite the retention device 414, although one of skill inthe art in possession of the present disclosure will appreciate that avariety of mechanisms may be utilized to release the retention device414 (an example of which is described below) while remaining within thescope of the present disclosure.

A network port connector ejection subsystem 418 is mounted to the board410 and located adjacent the computing device connector 412. In theillustrated embodiment, the network port connector ejection subsystem418 includes a network port connector ejection member 418 a that ismoveable relative to the network port connector ejection subsystem 418and towards the computing device connector 412 as discussed in furtherdetail below, and is coupled to the network port connector ejectionengine 402 (e.g., via a coupling between the network port connectorejection member 418 and the processing system in the remote accesscontroller discussed above). In a specific example, the network portconnector ejection subsystem 418 may be provided by a solenoid subsystem(e.g., a micro-solenoid) that is mounted to the board 410 adjacent thecomputing device connector 412, although one of skill in the art inpossession of the present disclosure will appreciate that a variety ofmechanisms may be utilized to engage a network port connector (anexample of which is described below) while remaining within the scope ofthe present disclosure. However, while a specific computing device 400has been illustrated, one of skill in the art in possession of thepresent disclosure will recognize that computing devices (or otherdevices operating according to the teachings of the present disclosurein a manner similar to that described below for the computing device400) may include a variety of components and/or component configurationsfor providing conventional computing device functionality, as well asthe functionality discussed below, while remaining within the scope ofthe present disclosure as well.

Referring now to FIG. 5, an embodiment of a computing device 500 isillustrated that may provide the network port connector ejection systemof the present disclosure. In an embodiment, the computing device 500may be provided by the IHS 100 discussed above with reference to FIG. 1and/or may include some or all of the components of the IHS 100, and inspecific examples may be provided by a server device. However, whileillustrated and discussed as being provided by a server device, one ofskill in the art in possession of the present disclosure will recognizethat the functionality of the computing device 500 discussed below maybe provided by other devices that are configured to operate similarly asthe computing device 500 discussed below (e.g., storage systems, switchdevices and/or other networking devices, and/or any other devicesincluding network ports.) In the illustrated embodiment, the computingdevice 500 includes a chassis 501 that houses the components of thecomputing device 500, only some of which are illustrated below. Forexample, the chassis 501 may house a processing system (not illustrated,but which may include the processor 102 discussed above with referenceto FIG. 1) and a memory system (not illustrated, but which may includethe memory 114 discussed above with reference to FIG. 1) that is coupledto the processing system and that includes instructions that, whenexecuted by the processing system, cause the processing system toprovide a network port connection ejection engine 504 that is configuredto perform the functionality of the network port connection ejectionengines and/or computing devices discussed below. In some examples, thenetwork port ejection engine 504 may be provided by a dedicated softwareprogram (e.g., that may be remotely operated), a management utilityprogram, via a remote access controller interface (as discussed below),and/or in a variety of other manners that would be apparent to one ofskill in the art in possession of the present disclosure. Furthermore,one of skill in the art in possession of the present disclosure willappreciate that the network port ejection engine 504 may includefirmware and, in some cases, electronics that are configured to operateand monitor the state of the network port connector ejection system.

As illustrated, the chassis 500 may also house a communication system504 that is coupled to the network port connection ejection engine 502(e.g., via a coupling between the communication system 504 and theprocessing system) and that may be provided by a Network InterfaceController (NIC), wireless communication systems (e.g., BLUETOOTH®, NearField Communication (NFC) components, WiFi components, etc.), and/or anyother communication components that would be apparent to one of skill inthe art in possession of the present disclosure. In a specific example,the computing device 500 may include a remote access controller such asa Baseboard Management Controller (BMC) like the integrated DELL® RemoteAccess Controller (iDRAC) available from DELL® Inc. of Round Rock, Tex.,United States, and the remote access controller may include the networkport connection ejection engine 502, along with a communication system504 illustrated in FIG. 5 that may be coupled to a secure managementnetwork that allows for secure management of the computing device 500.However, one of skill in the art in possession of the present disclosurewill appreciate that remote access controllers may be provided outsideof a chassis of a computing device, and thus the network port connectionejection engine 502 and communication system 504 may be located outsideof the chassis 501 while remaining within the scope of the presentdisclosure as well.

In the embodiment illustrated in FIG. 5, the computing device 500includes a wall 506 defining a network port connector system slot 508,and a board 510 (e.g., a circuit board or motherboard) is located in thechassis 501 adjacent the network port connector system slot 508. Acomputing device connector 512 in mounted to the board 510, and one ofskill in the art in possession of the present disclosure will recognizethat the computing device connector 512 may be coupled to components ofthe computing device 500 (e.g., the processing system, memory system,and/or other components discussed above) via traces that extend throughthe board, via cabling, and/or via other coupling subsystems known inthe art. A retention device 514 is included on the wall 506/network portconnector system slot 508, and in some of the embodiments discussedbelow may be any chassis element that one of skill in the art inpossession of the present disclosure would recognize is configured toengage the retention member 308 on the network port connector system 300to secure the base 320 in the network port connector system slot 508. Inthe illustrated embodiment, a retention device release subsystem 516 islocated adjacent the network port connector system slot 508 and coupledto the network port connector ejection engine 502 (e.g., via a couplingbetween the retention device release subsystem 516 and the processingsystem in the remote access controller discussed above). In theillustrated embodiment the retention device release subsystem 516includes a retention device release member 516 a that is moveablerelative to the retention device release subsystem 516 and into thenetwork port connector system slot 508, as discussed in further detailbelow. In a specific example, the retention device release subsystem 516may be provided by a solenoid subsystem (e.g., a micro-solenoid) that ismounted to the wall 506 opposite the outer surface of the chassis 501,although one of skill in the art in possession of the present disclosurewill appreciate that a variety of mechanisms may be utilized to releasethe retention member 308 (an example of which is described below) whileremaining within the scope of the present disclosure.

A network port connector ejection subsystem 518 is mounted to the board510 and located adjacent the computing device connector 512. In theillustrated embodiment, the network port connector ejection subsystem518 includes a network port connector ejection member 518 a that ismoveable relative to the network port connector ejection subsystem 518and towards the computing device connector 512 as discussed in furtherdetail below, and is coupled to the network port connector ejectionengine 502 (e.g., via a coupling between the network port connectorejection member 518 and the processing system in the remote accesscontroller discussed above). In a specific example, the network portconnector ejection subsystem 518 may be provided by a solenoid subsystem(e.g., a micro-solenoid) that is mounted to the board 510 adjacent thecomputing device connector 512, although one of skill in the art inpossession of the present disclosure will appreciate that a variety ofmechanisms may be utilized to engage a network port connector (anexample of which is described below) while remaining within the scope ofthe present disclosure. However, while a specific computing device 500has been illustrated, one of skill in the art in possession of thepresent disclosure will recognize that computing devices (or otherdevices operating according to the teachings of the present disclosurein a manner similar to that described below for the computing device500) may include a variety of components and/or component configurationsfor providing conventional computing device functionality, as well asthe functionality discussed below, while remaining within the scope ofthe present disclosure as well.

Referring now to FIG. 6, an embodiment of a method 600 for ejecting anetwork port connector is illustrated. As discussed below, the systemsand methods of the present disclosure provide the ability to remotelyphysically eject a network port connector in order disconnect thatnetwork port connector from a computing device connector in a mannerthat prevents reconnection of the network port connector and thecomputing device connector without being physically present at thecomputing device. For example, a computing device may include acomputing device connector that is configured to connect to a networkport connector, and a retention device that is configured to engage thenetwork port connector to secure the network port connector to thecomputing device connector. A retention device release subsystem isprovided in the computing device and coupled to the retention device,and is configured to be actuated to release the retention device fromengagement with the network port connector, and a network port connectorejection subsystem is provided in the computing device and is configuredto engage the network port connector (while the retention device releasesubsystem is actuated to release the retention device from engagementwith the network port connector) to move the network port connectorrelative to the computing device connector in order to disconnect thenetwork port connector from the computing device connector. As such,network access to a compromised or unauthorized computing device may beprevented in a manner that requires physical access to the computingdevice to regain network access, and without powering down the computingdevice such that remote troubleshooting of the computing device via asecure management network is available.

The method 600 begins at block 602 where a network port connector isconnected to a computing device connector in a computing device. Withreference to FIG. 7A, in an embodiment of block 602, the network portconnector device 200 may be positioned adjacent the network portconnector device slot 408 on the computing device 400 such that thenetwork port connector 212 on the network port connector device 200faces the network port connector device slot 408. The network portconnector device 200 may then be moved in a direction A such that thebase 202 of the network port connector device 200 enters the networkport connector device slot 408 and moves through the network portconnector device slot 408. As will be appreciated by one of skill in theart in possession of the present disclosure, the movement of the base202 of the network port connector device 200 through the network portconnector device slot 408 will cause the base 202 to engage theretention device 414 and move the retention device in a direction B,illustrated in FIG. 7B.

The base 202 of the network port connector device 200 may then continueto move through the network port connector device slot 408 (i.e., in thedirection A) until the network port connector 212 engages the computingdevice connector 412, which allows the retention device 414 to move in adirection C into the channel 210 defined by the cable connector end 206,as illustrated in FIG. 7C, in order to secure the network port connectordevice 200 in the network port connector device slot 408 with thenetwork port connector 212 engaging the computing device connector 412.As also illustrated in FIG. 7C, a cable 700 that is connected to anetwork (e.g., a Local Area Network LAN)) may be connected to thenetwork port connector device 200 in order to provide network access tothe computing device 400. As will be appreciated by one of skill in theart in possession of the present disclosure, a network administrator orother user that is physically present at the computing device 400 mayutilize the release element 206 to actuate the release subsystem 208,which operates to move the retention device 414 in the direction B andout of the channel 210, and allows for the removal of the network portconnector device 200 from the network port connector device slot 408.

With reference to FIG. 8A, in an embodiment of block 602, the networkport connector system 300 may be positioned adjacent the network portconnector system slot 508 on the computing device 500 such that thenetwork port connector 306 on the network port connector system 300faces the network port connector system slot 508. The network portconnector system 300 may then be moved through the network portconnector system slot 508 such that the base 302 moves through thenetwork port connector system slot 508. As will be appreciated by one ofskill in the art in possession of the present disclosure, the movementof the base 302 of the network port connector system 300 through thenetwork port connector system slot 508 will cause the retention member308 on the base 302 to engage the retention device 514 on the wall 506once the network port connector 306 has engaged the computing deviceconnector 512, as illustrated in FIG. 8A, in order to secure the networkport connector system 300 in the network port connector system slot 508with the network port connector 306 engaging the computing deviceconnector 512. As will be appreciated by one of skill in the art inpossession of the present disclosure, a network administrator or otheruser that is physically present at the computing device 400 may providea force on the retention member 308 to move the retention member 308towards the base 302, which operates to disengage the retention member308 from the retention device 514, and allows for the removal of thenetwork port connector system 300 from the network port connector systemslot 508.

The method 600 then proceeds to block 604 where the computing devicereceives an instruction to eject the network port connector. In anembodiment, at block 604, an instruction may be provided to thecomputing device 400 or 500 to eject the network port connector 212 or306, respectively, in order to disconnect that network port connector212 or 306 from the computing device connector 412 or 512, respectively.In some examples of block 604, a network administrator or other userthat is remote or otherwise not physically located with the computingdevice 400 or 500 may determine that the computing device has had itssecurity compromised via viruses, hacking attempts, and/or othercompromised security issues known in the art and, in response, maygenerate and transmit an instruction to eject the network port connector212 or 306 in order to disconnect that network port connector 212 or 306from the computing device connector 412 or 512, respectively.

In another example, the network administrator or other user that isremote or otherwise not physically located with the computing device 400or 500 may determine that that computing device 400 or 500 has beenconnected to a datacenter network without authorization (e.g., via theconnection of the network port connector 212 to the computing deviceconnector 412 on the computing device 400, or the connection of thenetwork port connector 306 to the computing device connector 512 on thecomputing device 500), and, in response, may generate and transmit aninstruction to eject the network port connector 212 or 306 in order todisconnect that network port connector 212 or 306 from the computingdevice connector 412 or 512, respectively. However, while a few specificexamples have been provided, one of skill in the art in possession ofthe present disclosure will appreciate that the instruction to eject thenetwork port connectors 212 or 306 in order to disconnect that networkport connector 212 or 306 from the computing device connector 412 or512, respectively, may be provided in response to any of a variety ofsituations that will fall within the scope of the present disclosure aswell.

As such, at block 604, the network port connector ejection engine 402may receive the instruction to eject the network port connector 212 (inorder to disconnect that network port connector 212 from the computingdevice connector 412) via a network and through the communication system404. Similarly, at block 604, the network port connector ejection engine502 may receive the instruction to eject the network port connector 306(in order to disconnect that network port connector 306 from thecomputing device connector 512) via a network and through thecommunication system 504. As will be appreciated by one of skill in theart in possession of the present disclosure, the network through whichthe instruction to eject the network port connectors 212 or 306 isreceived may be separate from the network available via the connectionof the network port connector 212 and the computing device connector412, or via the connection of the network port connector 306 and thecomputing device connector 512. For example, as discussed above, thecommunication systems 404 and 504 may be coupled to management networks,while the network port connector device 200 and the network portconnector system 300 may provide connections to a Local Area Network(LAN) in a datacenter that is separate from the management network.However, while a specific example is provided, one of skill in the artin possession of the present disclosure will appreciate that the networkthrough which the instruction to eject the network port connector isreceived may be provided by a variety of networks that are differentthan the network available via that network port connector whileremaining within the scope of the present disclosure as well.

The method 600 then proceeds to block 606 where the computing deviceactuates a retention device release subsystem to release a retentiondevice from engagement with the network port connector. With referenceto FIG. 7D, in an embodiment of block 606 and in response to receivingthe instruction to eject the network port connector 212, the networkport connector ejection engine 402 may actuate the retention devicerelease subsystem 414 to cause the retention device 414 to move in thedirection B and out of the channel 210 defined by the cable connectorend 206. For example, in embodiments in which the retention devicerelease subsystem 414 is provided by an electromagnet subsystem, atblock 606 the network port connector ejection engine 402 may providepower to the electromagnet subsystem included in the retention devicerelease subsystem 414 in order to produce a magnetic force that attractsthe metal material used to provide the retention device 414 (discussedabove), causing the retention device 414 to move in the direction B andout of the channel 210 defined by the cable connector end 206. However,while a specific retention device release mechanism is described, one ofskill in the art in possession of the present disclosure will appreciatethat a variety of mechanisms may be utilized to release the retentiondevice 414 from engagement with the network port connector device 200while remaining within the scope of the present disclosure as well.

With reference to FIG. 8B, in an embodiment of block 606 and in responseto receiving the instruction to eject the network port connector 306,the network port connector ejection engine 502 may actuate the retentiondevice release subsystem 516 to cause the retention device releasemember 516 a to move in a direction C and into the network portconnector system slot 508. As can be seen in FIG. 8B, the movement ofthe retention device release member 516 a into the network portconnector system slot 508 causes the retention device release member 516a to engage the retention member 308 and move the release member 308until it disengages the retention device 514. For example, inembodiments in which the retention device release subsystem 516 isprovided by a solenoid subsystem, at block 606 the network portconnector ejection engine 402 may provide power to the solenoidsubsystem included in the retention device release subsystem 516 inorder to cause the retention device release member 516 a to move in thedirection C and into the network port connector system slot 508 toengage the retention member 308 to disengage it from the retentiondevice 514. However, while a specific retention device release mechanismis described, one of skill in the art in possession of the presentdisclosure will appreciate that a variety of mechanisms may be utilizedto release the retention device 514 from engagement with the networkport connector system 300 while remaining within the scope of thepresent disclosure as well.

The method 600 then proceeds to block 608 where the computing deviceactuates a network port connector ejection subsystem to disconnect thenetwork port connector from the computing device connector. Withreference to FIG. 7E, in an embodiment of block 608, in response toreceiving the instruction to eject the network port connector 212, andfollowing the actuation of the retention device release subsystem 416 todisengage the retention device 414 from the network port connectordevice 200, the network port connector ejection engine 402 may actuatethe network port connector ejection subsystem 418 to cause the networkport connector ejection member 418 a to move in a direction D and intoengagement with the base 202 of the network port connector device 200.As can be seen in FIG. 7F, the engagement of the network port connectorejection member 418 a with the base 202 of the network port connectordevice 200 and the continued movement of the network port connectorejection member 418 a (i.e., in the direction D) causes the base 202 ofthe network port connector device 200 to move in a direction E relativeto the computing device connector 412 such that the network portconnector 212 is disconnected from the computing device connector 412.As will be appreciated by one of skill in the art in possession of thepresent disclosure, the disengagement of the retention device 414 fromthe network port connector device 200 allows for the movement of thenetwork port connector device 200 in the direction E in order todisconnect the network port connector 212 from the computing deviceconnector 412.

For example, in embodiments in which the network port connector ejectionsubsystem 418 is provided by a solenoid subsystem, at block 608 thenetwork port connector ejection engine 402 may provide power to thesolenoid subsystem included in the network port connector ejectionsubsystem 418 in order to cause the network port connector ejectionmember 418 a to move in the direction D and into engagement with thebase 202 of the network port connector device 200 to disconnect thenetwork port connector 212 from the computing device connector 412.However, while a specific network port connector ejection mechanism isdescribed, one of skill in the art in possession of the presentdisclosure will appreciate that a variety of mechanisms may be utilizedto disconnect the network port connector 212 from the computing deviceconnector 412 while remaining within the scope of the present disclosureas well. Furthermore, one of skill in the art in possession of thepresent disclosure will recognize that the distance that the networkport connector device 200 is moved may be relatively short (e.g., a fewmillimeters) in order to break the connection between the network portconnector 212 and the computing device connector 412. As illustrated inFIG. 7G, subsequent to the disconnection of the network port connector212 from the computing device connector 412, the network port connectorejection engine 402 may stop actuating the retention device releasesubsystem 416 and the network port connection ejection subsystem 418.

With reference to FIG. 8C, in an embodiment of block 608, in response toreceiving the instruction to eject the network port connector 306, andfollowing the actuation of the retention device release subsystem 516 todisengage the retention device 514 from the network port connectorsystem 300, the network port connector ejection engine 502 may actuatethe network port connector ejection subsystem 518 to cause the networkport connector ejection member 518 a to move in a direction F and intoengagement with the base 302 of the network port connector system 300.As can be seen in FIG. 8C, the engagement of the network port connectorejection member 518 a with the base 302 of the network port connectorsystem 300 and the continued movement of the network port connectorejection member 518 a (i.e., in the direction F) causes the base 302 ofthe network port connector system 300 to move in a direction G relativeto the computing device connector 512 such that the network portconnector 306 is disconnected from the computing device connector 512.As will be appreciated by one of skill in the art in possession of thepresent disclosure, the disengagement of the retention device 514 fromthe network port connector system 300 allows for the movement of thenetwork port connector system 300 in the direction G in order todisconnect the network port connector 306 from the computing deviceconnector 512.

For example, in embodiments in which the network port connector ejectionsubsystem 518 is provided by a solenoid subsystem, at block 608 thenetwork port connector ejection engine 502 may provide power to thesolenoid subsystem included in the network port connector ejectionsubsystem 518 in order to cause the network port connector ejectionmember 518 a to move in the direction F and into engagement with thebase 302 of the network port connector device 300 to disconnect thenetwork port connector 306 from the computing device connector 512.However, while a specific network port connector ejection mechanism isdescribed, one of skill in the art in possession of the presentdisclosure will appreciate that a variety of mechanisms may be utilizedto disconnect the network port connector 306 from the computing deviceconnector 512 while remaining within the scope of the present disclosureas well. Furthermore, one of skill in the art in possession of thepresent disclosure will recognize that the distance that the networkport connector system 300 (e.g., the base 302) is moved may berelatively short (e.g., a few millimeters) in order to break theconnection between the network port connector 306 and the computingdevice connector 512. As illustrated in FIG. 8D, subsequent to thedisconnection of the network port connector 306 from the computingdevice connector 512, the network port connector ejection engine 502 maystop actuating the retention device release subsystem 516 and thenetwork port connection ejection subsystem 518.

While the examples above illustrated and describe a situation in which asingle network port connector is ejected, one of skill in the art inpossession of the present disclosure will appreciate that computingdevices may include multiple network port connectors connected torespective computing device connectors included in the computing device.As such, one of skill in the art in possession of the present disclosurewill appreciate how the teachings of the present disclosure may beapplied to such systems to eject multiple network port connectors (e.g.,at the same time) while remaining within the scope of the presentdisclosure as well.

Thus, systems and methods have been described that provide the abilityto remotely physically eject an SFP transceiver device in orderdisconnect that SFP transceiver device from a server device connector ina manner that prevents reconnection of the SFP transceiver device andthe server device connector without being physically present at theserver device. For example, a server device may include a server deviceconnector that is configured to connect to an SFP transceiver device,and a retention device that is configured to engage the SFP transceiverdevice to secure the SFP transceiver device to the server deviceconnector. A retention device release subsystem is provided in theserver device coupled to the retention device, and is configured to beactuated to release the retention device from engagement with the SFPtransceiver device, and a SFP transceiver device ejection subsystem isprovided in the server device and is configured to engage the SFPtransceiver device (while the retention device release subsystem isactuated to release the retention device from engagement with the SFPtransceiver device) to disconnect the SFP transceiver device from theserver device connector. As such, network access to a compromised orunauthorized server device may be prevented in a manner that requiresphysical access to the server device to regain network access, andwithout powering down the server device such that remote troubleshootingof the server device using a remote access controller and via a securemanagement network is available.

Although illustrative embodiments have been shown and described, a widerange of modification, change and substitution is contemplated in theforegoing disclosure and in some instances, some features of theembodiments may be employed without a corresponding use of otherfeatures. Accordingly, it is appropriate that the appended claims beconstrued broadly and in a manner consistent with the scope of theembodiments disclosed herein.

1. A network port connector ejection system, comprising: a computingdevice connector that is configured to connect to a network portconnector; a retention device that is configured to engage the networkport connector to secure the network port connector to the computingdevice connector; a retention device release subsystem that is coupledto the retention device and that is configured, in response to receivingan instruction to disconnect the network port connector from thecomputing device connector, to be actuated to release the retentiondevice from engagement with the network port connector; and a networkport connector ejection subsystem that is configured, in response to thereceiving the instruction to disconnect the network port connector fromthe computing device connector, following the actuation of the retentiondevice release subsystem, and while the retention device releasesubsystem is actuated to release the retention device from engagementwith the network port connector, to engage the network port connector todisconnect the network port connector from the computing deviceconnector.
 2. The system of claim 1, wherein the network port connectoris a Small Form-factor Pluggable (SFP) transceiver device.
 3. The systemof claim 1, wherein the retention device includes a metal material, andwherein the retention device release subsystem includes an electromagnetdevice that is configured to attract the metal material in the retentiondevice to cause the retention device to move and release from engagementwith the network port connector.
 4. The system of claim 1, wherein thenetwork port connector ejection subsystem includes a solenoid devicehaving a network port connector engagement member that is configured,when the network port connector ejection system is actuated, to engagethe network port connector to disconnect the network port connector fromthe computing device connector.
 5. The system of claim 1, furthercomprising: a communication system coupled to the retention devicerelease subsystem and the network port connector ejection subsystem,wherein the retention device release subsystem is configured to beactuated and the network port connector ejection subsystem is configuredto engage the network port connector in response to instructionsreceived through a network via the communication system.
 6. The systemof claim 1, wherein the network port connector is an Ethernet cableconnector.
 7. An Information Handling System (IHS), comprising: aprocessing system; and a memory system that is coupled to the processingsystem and that includes instructions that, when executed by theprocessing system, cause the processing system to provide a network portconnector ejection engine that is configured to: receive an instructionto eject a network port connector that is connected to a computingdevice connector; actuate, in response to receiving the instruction toeject the network port connector, a retention device release subsystemthat is coupled to a retention device to release the retention devicefrom engagement with the network port connector; and actuate, inresponse to receiving the instruction to eject the network portconnector, following the actuation of the retention device releasesubsystem, and while the retention device release subsystem is actuatedto release the retention device from engagement with the network portconnector, a network port connector ejection subsystem to engage thenetwork port connection ejection subsystem with the network portconnector to disconnect the network port connector from the computingdevice connector.
 8. The IHS of claim 7, wherein the network portconnector is a Small Form-factor Pluggable (SFP) transceiver device. 9.The IHS of claim 7, wherein the retention device includes a metalmaterial, and wherein the retention device release subsystem includes anelectromagnet device that is configured to attract the metal material inthe retention device to cause the retention device to move and releasefrom engagement with the network port connector.
 10. The IHS of claim 7,wherein the network port connector ejection subsystem includes asolenoid device having a network port connector engagement member thatis configured, when the network port connector ejection system isactuated, to engage the network port connector to disconnect the networkport connector from the computing device connector.
 11. The IHS of claim7, further comprising: a communication system coupled to the networkport connector ejection engine, wherein the network port connectorejection engine is configured to actuate the retention device releasesubsystem and the network port connector ejection subsystem in responseto instructions received through a network via the communication system.12. The IHS of claim 7, wherein the network port connector is anEthernet cable connector.
 13. The IHS of claim 12, wherein the retentiondevice release subsystem is configured to engage the Ethernet cableconnector to release the retention device from engagement with theEthernet cable connector.
 14. A method for ejecting a network portconnector, comprising: receiving, by a computing device, an instructionto eject a network port connector that is connected to a computingdevice connector; actuating, by the computing device in response toreceiving the instruction to eject the network port connector, aretention device release subsystem that is coupled to a retention deviceto release the retention device from engagement with the network portconnector; and actuating, by the computing device in response toreceiving the instruction to eject the network port connector, followingthe actuation of the retention device release subsystem, and while theretention device release subsystem is actuated to release the retentiondevice from engagement with the network port connector, a network portconnector ejection subsystem to engage the network port connectionejection subsystem with the network port connector to disconnect thenetwork port connector from the computing device connector.
 15. Themethod of claim 14, wherein the network port connector is a SmallForm-factor Pluggable (SFP) transceiver device.
 16. The method of claim14, wherein the retention device includes a metal material, and whereinthe retention device release subsystem includes an electromagnet devicethat is configured to attract the metal material in the retention deviceto cause the retention device to move and release from engagement withthe network port connector.
 17. The method of claim 14, wherein thenetwork port connector ejection subsystem includes a solenoid devicehaving a network port connector engagement member that is configured,when the network port connector ejection system is actuated, to engagethe network port connector to disconnect the network port connector fromthe computing device connector.
 18. The method of claim 14, furthercomprising: receiving, by the computing device through a network via acommunication system, instructions to actuate the retention devicerelease subsystem and the network port connector ejection subsystem. 19.The method of claim 14, wherein the network port connector is anEthernet cable connector.
 20. The method of claim 19, wherein theretention device release subsystem is configured to engage the Ethernetcable connector to release the retention device from engagement with theEthernet cable connector.